home *** CD-ROM | disk | FTP | other *** search
- Path: FreeNet.Carleton.CA!de351
- From: de351@FreeNet.Carleton.CA (K. C. Lee)
- Newsgroups: comp.sys.amiga.programmer
- Subject: Re: toy operating systems, like AmigaOS
- Date: 20 Apr 1996 21:45:42 GMT
- Organization: The National Capital FreeNet
- Sender: de351@freenet3.carleton.ca (K. C. Lee)
- Message-ID: <4lblu6$h9f@freenet-news.carleton.ca>
- References: <skllsf.984983.4.5@groomlake.mil> <4kplgo$o9r@canyon.sr.hp.com> <4ksu6q$haa@nadine.teleport.com> <19960417.7BBC9E0.3B7F@asd01-01.dial.xs4all.nl> <4l4cha$dhn@daily-planet.execpc.com> <19960420.7B93528.C5E8@asd10-02.dial.xs4all.nl>
- Reply-To: de351@FreeNet.Carleton.CA (K. C. Lee)
- NNTP-Posting-Host: freenet3.carleton.ca
-
- >> May I point out again that until programming methods improve drastically,
- >> *all* non-trivial software will have bugs. The user still needs some
- >> protection, because sooner or later, something will break.
-
- The common programming PRACTICE and proper testing techniques need to be
- improved. These are some of the stuff that the average C0DERs (not
- programmers !) will never learn until they get the necessary formal education.
-
- If they build chips like we write programs, then it would take 10 to 20
- revisions before you get something close to bug free. These bugs are less
- often (Pentium bugs and other not so famous ones) because they do a lot of
- testing and simulations before committing.
-
- Jeroen T. Vermeulen (jtv@xs4all.nl) writes:
-
- > In my experience the worst problem with bugs is not so much when they don't
- > occur until the customer bumps into them, but when they do occur yet produce no
- > noticable effect during testing. Hence my preference for a split system
-
- One is supposed to produce a test suite to test all possible logical paths
- as well as results of a program. Anything less, you get bugs. In real
- life, there is a trade-off between how fast you want the product to be out
- and what kind of bugs you can tolerate.
-
- K. C. Lee
-
-